Usage is a platform surface, not an installed app - #264
Merged
Conversation
The shell reads an extension's `builtin` flag as "this is an app": the roster's non-builtin entries get registered into the UI registry, which puts them in the switcher and mounts generic pages at /<name>. Usage never set the flag, so it drew a dropdown entry, and its generic home page shadowed the shell's own /usage route — the pill in the appbar landed on an empty subject board instead of the usage panel. The shell's routes now come before the extension routes in the switch, so a platform path can't be taken by an extension named after it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The shell reads an extension's
builtinflag as "this is an app": every non-builtin roster entry is registered into the UI registry, which gives it a switcher entry and mounts generic pages at/<name>.Usage never set the flag, so it showed up as an app in the dropdown, and the generic home page it got at
/usageshadowed the shell's own usage route — clicking the quota pill landed on an empty subject board instead of the usage panel.Usage now declares
builtin = True, alongside core.The shell's own routes also move ahead of the extension routes in the switch, so a platform path stays with the platform even if an extension is named after one.
🤖 Generated with Claude Code